Skip to content

New version: MotifInference v0.1.9 - #165363

Open
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-motifinference-e1c1f7b9-v0.1.9-0c7718a7a9
Open

New version: MotifInference v0.1.9#165363
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-motifinference-e1c1f7b9-v0.1.9-0c7718a7a9

Conversation

@JuliaRegistrator

Copy link
Copy Markdown
Contributor
## Features
- Requires SEQ2EXPdata >= 1.1.1, which adds the `wild_type` keyword to
  `SEQ2EXP_Dataset`. It pins the mutation encoding's reference sequence rather
  than taking a per-column plurality vote, which is unreliable in a saturating
  library where the wild-type residue is a minority at the mutated positions.
- Not yet forwarded by MotifInference's own entry points: pass it by building
  the `SEQ2EXP_Dataset` yourself and calling `run_method(trc, data)`.

## Breaking changes
- None. No MotifInference API, default, or export changed; only the allowed
  SEQ2EXPdata range narrows, and 1.1.1 is additive over 1.1.0.

UUID: e1c1f7b9-3d4a-4d3e-9b6a-2f5c8d1a7b34
Repo: https://github.com/kchu25/MotifInference.jl.git
Tree: f867b154d8c2d743ce3d128bfb64cc9a7c49e833

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@github-actions

Copy link
Copy Markdown
Contributor

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines which are not met ❌

  • I was not able to install the package (i.e. Pkg.add("MotifInference") failed). See the AutoMerge logs for details.
  • I was not able to load the package (i.e. import MotifInference failed). See the AutoMerge logs for details.

2. Needs action: here's what to do next

  1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
  2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant